System of centrally managing core reference data associated with an enterprise

ABSTRACT

A system is provided for centrally managing core enterprise reference data associated with an enterprise. A centralized master repository contains the core enterprise reference data. The internal services framework also provides internal services for managing the core enterprise reference data within the centralized master repository, one or more of the internal services having direct access to the core enterprise reference data stored in the centralized master repository for management purposes. An infrastructure services layer coupled to the centralized master repository provides for bulk data transfers of core enterprise reference data between the centralized master repository and one or more external operational systems according to one or more enterprise-level business workflows, the external operational systems permitted indirect access to the core enterprise reference data stored in the centralized master repository for operational purposes.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation application of U.S. patent application Ser. No.11/697,966 filed on Apr. 9, 2007, now U.S. Pat. No. 8,725,678 entitled“System of Centrally Managing Core Reference Data Associated with anEnterprise”, which is a divisional of U.S. patent application Ser. No.10/847,422 entitled “Master Data Management System for CentrallyManaging Core Reference Data Associated with an Enterprise”, filed May17, 2004, which is a continuation of U.S. patent application Ser. No.10/755,437 filed Jan. 12, 2004 entitled “Master Data Management Systemfor Centrally Managing Cached Data Representing Core EnterpriseReference Data Maintained as Locked in True State Read Only Access untilCompletion of Manipulation”, now U.S. Pat. No. 7,213,037 which claimsthe benefit under 35 U.S.C. §119(e) of U.S. Provisional Application No.60/469,501 filed May 9, 2003 entitled “System for Centrally ManagingCore Reference Data Associated with an Enterprise” and U.S. ProvisionalApplication No. 60/439,864 filed Jan. 13, 2003 entitled “BusinessConfiguration Management System”.

U.S. patent application Ser. No. 10/847,422, U.S. Pat. Nos. 8,725,678and 7,213,037, and U.S. Provisional Application Nos. 60/469,501 and60/439,864 are commonly assigned to the assignee of the presentapplication. The disclosure of related U.S. patent application Ser. No.10/847,422, U.S. Pat. Nos. 8,725,678 and 7,213,037, and U.S. ProvisionalApplication Nos. 60/469,501 and 60/439,864 are hereby incorporated byreference into the present disclosure as if fully set forth herein.

TECHNICAL FIELD

This invention relates generally to enterprise management solutions, andmore particularly to a master data management (MDM) system used forcentrally managing core reference data associated with an enterprise.

BACKGROUND

An enterprise may use a data management system to address management ofenterprise data. A considerable amount of data is required to adequatelydefine an enterprise. The data may be of two fundamental types. A firsttype of data, which may be referred to as core enterprise referencedata, describes the structure and characteristics of the enterprise andits entities and is not transient or transactional in nature. This typeof data may be associated with enterprise data masters and may be storedin a core reference data repository, although such data is notrestricted to the type of data associated with traditional enterprisedata masters. Efficient handling this data is critical, as is orderlyand process-driven management of the state of the data. Use of this datais, in general, not limited to particular portions of the enterprise;rather, this data is typically used pervasively throughout theenterprise and with its value chain partners. The second type of data,which may be referred to as operational data, is transient transactionaldata required by planning, execution, monitoring, or other enterprisesolution components. This type of data is typically not stored in thecore reference data repository; the data management system provides astaging and distribution framework for such data. A problem facing manyenterprises is to create a system that provides for effective andscalable management, distribution, and use of both its core enterprisereference data and its transactional data in a manner that servicesneeds for this data within the enterprise as a whole and also specificneeds of planning, execution, monitoring, and other enterprise solutioncomponents associated with the enterprise.

SUMMARY

In one embodiment, a system is provided for centrally managing coreenterprise reference data associated with an enterprise. A centralizedmaster repository contains the core enterprise reference data. Aninternal services framework coupled to the centralized master repositoryprovides a business process toolkit for managing models associated withthe system. The business process toolkit includes a model librarycontaining data models and one or more modeling services for modelingthe system, its structure, and its components. The internal servicesframework also provides internal services for managing the coreenterprise reference data within the centralized master repository, oneor more of the internal services having direct access to the coreenterprise reference data stored in the centralized master repositoryfor management purposes. An infrastructure services layer coupled to thecentralized master repository provides for bulk data transfers of coreenterprise reference data between the centralized master repository andone or more external operational systems according to one or moreenterprise-level business workflows, the external operational systemsbeing permitted indirect access to the core enterprise reference datastored in the centralized master repository for operational purposes.

Particular embodiments of the present invention may provide one or moretechnical advantages. For example, certain embodiments may provide anenterprise framework incorporating classification into configuration,planning, execution, and monitoring segments. Certain embodiments mayprovide a secure system of record optimized in architecture and designfor management of core enterprise reference data. Certain embodimentsmay allow for full or partial automation of important time- andlabor-intensive business processes according to embeddedenterprise-level business workflows. Certain embodiments may provideall, some, or none of these technical advantages. Certain embodimentsmay provide one or more other technical advantages, one or more of whichmay be readily apparent to those skilled in the art from the figures,description, and claims included herein.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present invention andthe features and advantages thereof, reference is made to the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates an example enterprise application framework includingan MDM system;

FIG. 2 illustrates an example high level logical business architecturefor an MDM system;

FIG. 3 illustrates an example high level logical technical architecturefor an MDM system;

FIG. 4 illustrates an example high level logical data servicesarchitecture for an MDM system;

FIG. 5 illustrates an example high level logical architecture of an MDMdatabase;

FIG. 6 illustrates an example information sharing architecture for anMDM system;

FIG. 7 illustrates an example MDM studio and an associated MDM modellibrary;

FIG. 8 illustrates an example MDM use model;

FIG. 9 illustrates an example high level physical architecture for anMDM system; and

FIG. 10 illustrates an example new item introduction process providedwithin an MDM system.

DETAILED DESCRIPTION

I. Enterprise Solution Framework

FIG. 1 illustrates an example enterprise solution framework 2 includinga Master Data Management (MDM) system 4. In one embodiment, framework 2includes a classification of an associated enterprise into fourfundamental segments: (1) configuration of the enterprise and itsentities; (2) planning with respect to the enterprise and its entities;that is, decisions about what to do; (3) execution with respect to theenterprise and its entities; that is, acting upon those decisions; and(4) monitoring with respect to the enterprise and its entities; that is,monitoring the results of those decisions and supplying feedback to theconfiguration and planning segments accordingly. In this embodiment, MDMsystem 4 represents the configuration segment, while the planning,execution, and monitoring enterprise solution components 6 represent theplanning, execution, and monitoring segments, respectively.

MDM system 4 provides centralized storage and management of enterprisereference data, maintaining reference data and associated datamanagement processes separate from enterprise solution components 6 andassociated operational processes while making reference data availableto enterprise solution components 6 for consumption as needed.Centralized storage and management of reference data for existing andfuture enterprise solution components 6 may facilitate extension orother modification of enterprise solution components 6 without needingto modify reference data within MDM system 4. Centralized storage andmanagement of reference data may also facilitate integration ofenterprise solution components 6, for example, when one enterprisesolution component 6 is replaced with another or an enterprise solutioncomponent providing an entirely new business function is introduced.Centralized storage and management of reference data may furtherfacilitate integration of one enterprise into another, for example, inconnection with a merger or acquisition.

Infrastructure services 8 provide bulk data transfer and enterprisemessaging between MDM system 4 and enterprise solution components 6 inaccordance with business workflows operating in association withinfrastructure services 8. These workflows, which may be embeddedpartially within MDM system 4 and partially within infrastructureservices 8, may incorporate customized business best practices of theenterprise. In addition, these workflows may be wholly or partiallyautomated using an appropriate enterprise-level workflow engine andappropriate MDM system resources available to that workflow engine.

II. MDM Logical Business Architecture

FIG. 2 illustrates an example high level logical business architecture10 for an MDM system 4. In general, the logical business architecturerepresents a business-centric view of MDM system 4 and includes corebusiness processes, services, and data elements that MDM system 4 may berequired to provide depending on the nature of the enterprise associatedwith MDM system 4. In one embodiment, MDM system 4 includes a processlayer 12 that provides a context for implementing and wholly orpartially automating business configuration processes 14. A servicelayer 16 underlying process layer 12 provides services 18 providingfunctions enabling process tasks that are appropriate for processes 14.A data layer 20 underlying service layer 16 provides base data modelsand physical representations for storing core enterprise reference data22 for retrieval and use in connection with processes 14 and associatedservices 18.

An understanding of the fundamental concepts relating to the purposesand functions of MDM system 4 may aid in understanding the MDMarchitecture. At the core of MDM system 4 is the concept of datamanagement, which encompasses both what data is stored and how that datais stored and made available for use. Since MDM system 4 is primarilyconcerned with structural data describing the enterprise or, moreprecisely, with data associated with entities within the businessstructure of the enterprise, the focus of the MDM architecture is on thestorage, management, and retrieval of data associated with entities orwith relationships between entities. In one embodiment, MDM system 4provides such data storage, management, and retrieval using a core MDMreference data repository based on a multidimensional databaseconstruct.

Consider the following example. One example of an entity associated witha retail enterprise is an item. Items may have attributes such as size,weight, color, etc. If a particular entity, in this case a particularitem, is considered a coordinate in a first dimension representingitems, then the attributes of the particular item entity are associatedwith the coordinate for the particular item in the item dimension. Atthis point, the example involves only a one-dimensional line space,where discrete points on the line represent particular items.

Another example of an entity associated with an enterprise is a store orother location. Locations may have attributes such as size, physicaladdress, etc. Like the particular item discussed above, a particularlocation may be considered a coordinate in a second dimensionrepresenting locations, where the attributes of the particular locationentity are associated with the coordinate for the particular location inthe location dimension. At this point, the example involves twoone-dimensional line spaces, where discrete points on the first linerepresent particular items and discrete points on the second linerepresent particular locations. The example may be extended to includeattributes that depend on the combination of a particular item and aparticular location. Neither the item dimension nor the locationdimension alone will suffice to store such multi-dimensional attributes.However, if the item and location dimensions are viewed as axes, andeach intersection of item and location coordinates within an areadefined by an orthogonal arrangement of these axes is viewed as a (item,location) point in two-dimensional entity space at which such attributesare stored, the concept becomes clear.

The example can be further extended to include attributes that depend onthe combination of any number of arbitrary entity dimensions, leading tothe concept of attributes as generalized data stored at and retrievedfrom points in an n-dimensional entity space. For example, a particularthree-dimensional entity space suitable for an example retail enterprisemight include item, location, and time dimensions, where attributesstored at each (item, location, time) point within a volume defined byan orthogonal arrangement of these axes corresponds to a particularcombination of entities in the item, location, and time dimensions. Inone embodiment, all reference data 22 stored within MDM system 4 may beequivalent to an attribute associated with a point in n-dimensionalentity space.

In one embodiment, an overriding characteristic of all data that isconsidered for inclusion within MDM system 4 is the multi-dimensionaldatabase construct described above. Hence, a core architecturalprinciple for MDM system 4 may be to accommodate a dimensional datastructure as a core element in every component of MDM system 4. This mayhave several important implications for the MDM architecture and design.Such important implications may include, without limitation: (1) aconsistent mechanism for locating points in an n-dimensional entityspace; (2) a consistent mechanism for storing data at and retrievingdata from points in an n-dimension entity space; and (3) ensuring thatall distinct data storage components support the above.

Another fundamental concept for MDM system 4 may involve optimization ofthe physical architecture and database structures for the desiredfunctions of MDM system 4. The core MDM reference data repository, asdescribed above, is primarily for data management and is structured toprovide a rich data management framework. On the other hand, input andoutput data staging and distribution elements of MDM system 4 mayrequire efficient data transfer and throughput. While many systems haveattempted to provide a compromise architecture to handle all such needs,MDM system 4 is preferably structured so that each element is designedto optimally accomplish its corresponding functions.

MDM system 4 may provide value for enterprises in various industrysettings, such as retailing, manufacturing, or other industry settings.Although retail examples may be provided for purposes of illustration,the present invention contemplates MDM system 4 being used in connectionwith, and being tailored to, any suitable enterprise. The MDMarchitecture and design are preferably constructed to provide elementssuitable to allow for successful deployment of MDM system 4 acrossmultiple industry types and multiple enterprises within a particularindustry type.

A. Process Layer

As described above, MDM system 4 includes a process layer 12 thatprovides the context for implementing and wholly or partially automatingbusiness configuration processes 14. In general, processes 14 providefunctions necessary to realize process workflows provided as part of theMDM solution, providing structure to enterprise activities and enablingthose activities to be repeated, controlled, monitored, and improvedover time. Each process 14 represents a sequence of tasks that togetheraccomplish a business activity. MDM system 4 may provide native supportfor generic processes 14 and support specific to particular processes14. In one embodiment, processes 14 allow rich business workflows to beembedded within MDM system 4 and supported using the resources withinunderlying service and data layers 16 and 20, respectively. In oneembodiment, MDM system 4 provides a highly configurable, flexible, andextensible environment for implementing and wholly or partiallyautomating any suitable processes 14.

Processes 14 may operate at two levels. The first level, the enterpriselevel, may include larger scale intra-enterprise and inter-enterpriseprocesses 14 associated with management of data as it relates to thetargeted goals of the MDM solution. For example, where MDM system 4 isassociated with a retail enterprise, an example of a first level process14 may be a new item introduction process 14 involving storage ofexternally generated data concerning a new item into the core MDMreference data repository. The second level may include smaller scalemanagement processes 14 involving movement of data internal to MDMsystem 4, such as retrieval of data from the core MDM reference datarepository in accordance with queries from user interface, analytics, orother services internal to MDM system 4.

For example, generic processes 14 that may apply to any enterprise andany dimension of MDM system 4 may include, without limitation: (1) newentity introduction; (2) entity maintenance; (3) metadata realignment;(4) entity extraction; and (5) entity replication.

1. New Entity Introduction

This process 14 represents the introduction of a new entity into MDMsystem 4. For an example retail enterprise, this may include introducinga new item, location, vendor, or customer. The process 14 may beinitiated by the enterprise associated with MDM system 4 or by any otherenterprise, such as a vendor of a new item being introduced. A vendorproviding a new item may be considered an example of content exchange.In any case, the retail enterprise associated with MDM system 4 must addenterprise specific data to MDM system 4 for the new item, validate thedata, approve use of the new item, and publish the new item as availablefor use by planning, execution, monitoring, or other enterprise solutioncomponents 6, possibly through replication. An example new itemintroduction process 14 is described more fully below with reference toFIG. 10.

2. Entity Maintenance

This process 14 involves updating one or more characteristics of anexisting entity, such as an item, location, vendor, or customer for anexample retail enterprise. The process 14 may be initiated by theenterprise associated with MDM system 4 or by any other enterprise, suchas a vendor of an item for which one or more characteristics are to beupdated. For example, an “improved” item may effectively retain itsoriginal part number and Stock Keeping Unit (SKU) but have one or moreof its primary attributes altered by the vendor, such as its size,weight, or color. Similarly, the retail enterprise might alter one ormore secondary attributes of an existing item.

3. Metadata Realignment

This process 14 involves movement within a dimension of one of moremembers of one level relationship to another level relationship in adimensional hierarchy. For example, a retail enterprise might move anitem from one class to another class, which would in turn requireidentification of the one or more members to alter the targetrelationships. The process 14 may need to keep appropriate audit andjournal trails, which may require one or more approval sub-processes.

4. Entity Extraction

This process 14 involves providing selection criteria for one or moreentities, performing an appropriate query, and moving appropriate dataor otherwise making the data available to the requesting role subsystem.

5. Entity Replication

This process 14 involves systematic replication of data in MDM system 4in whole or in part to other subsystems for internal use. Suchreplication may allow the data to be used in a more efficient fashionthan through direct operational access to the core MDM reference datarepository.

B. Service Layer

As described above, service layer 16 provides services 18 that providefunctions enabling the construction of process tasks appropriate forprocesses 14. Each service 18 provides a useful unit of work or enablesa process task in the context of MDM system 4. Services 18 are notprocesses 14; rather, a service 18 is more analogous to a task within aprocess 14 or an action in response to a request associated with aprocess 14, such as computing the value of a function associated withthe service 18 or issuing a query to view, update, or delete informationin the core MDM reference data repository. In one embodiment, services18 within service layer 16 of MDM system 4 may include, withoutlimitation: (1) entity maintenance services 18 a; (2) metadatamaintenance services 18 b; (3) parameter maintenance services 18 c; (4)attribute/trait services 18 d; (5) event (calendar) services 18 e; (6)supply chain network services 18 f; (7) sourcing services 18 g; (8)activity based costing (ABC) services 18 h; (9) contract services 18 i;and (10) bill of materials (BOM) services 18 j.

1. Entity Maintenance

Entity maintenance services 18 a provide basic functions for navigating,accessing, filtering, and sorting entities within MDM system 4. For anexample retail enterprise, items, locations, vendors, and customers maybe types of entities that are managed within MDM system 4 and maintainedusing entity maintenance services 18 a.

2. Metadata Maintenance

Metadata maintenance services 18 b provide basic functions for theconstruction, management, and realignment of appropriate metadata. Forexample, such metadata may include metadata describing the enterprise asa whole, the structure of MDM system 4, the structures of the datastaging areas of MDM system 4, and the relationships between the datastaging areas and the core MDM reference data repository. Such functionsmay include the ability to create dimensions and to define hierarchieson the dimension spaces, where each hierarchy includes a number oflevels each having a number of members. Such functions may also includemaintenance with respect to dimensions, levels, and members, such ascreation, modification, or deletion of such metadata elements.

3. Parameter Maintenance

Parameter maintenance services 18 c provide basic functions for themaintenance, management, and distribution of enterprise solutioncomponent parameters (i.e. business rule parameters). One or moreparameters may be, but are not required to be, specific to one or moreparticular enterprise solution components 6. Each parameter may be tiedto one or more entities and, as such, may be viewed as a secondaryattribute of the entities (as opposed to a primary attribute such assize, weight, and color of an example item). Parameter maintenanceservices 18 c provide functions particularly appropriate for these typesof attributes. MDM system 4 may not only provide storage for suchattributes and enable retrieval of such attributes for use, but may alsoprovide a standardized management paradigm for all parameters in theoverall enterprise solution. In one embodiment, this has the beneficialeffect of providing a uniform methodology for parameter management andrelieves point solution components from providing such functionality.

4. Attribute/Trait Services

Some attributes of entities are quantitative, well-defined, and stableover time. Examples of such attributes might include the size, weight,and color of an item or the address of a vendor. Other types ofattributes are more qualitative, not as well-defined, and may changeover time. These attributes, which may be referred to as traits, areoften useful for customer-centric marketing and serve as the basis forattribute/trait cluster generation. Attribute/Trait services 18 dprovide functions appropriate for this type of data residing within ormanaged using MDM system 4. Since the number, and even the types, ofsuch attributes/traits are typically not known a priori, therequirements for the physical structure of a system to handle this typeof data are somewhat different than for more static master data.Attribute/Trait services 18 d provide basic functions for creating,maintaining, and using this type of data and may also include moresophisticated services such as attribute/trait clustering services.

5. Event (Calendar) Services

Event, or more generally calendar, services 18 e deal with management oftime-related activities. These services 18 e provide basic functions forestablishing reference calendars and for creating and managingtime-related activities (i.e. events with respect to establishedcalendars).

6. Supply Chain Network Services

Supply chain network services 18 f provide basic functions forsupporting the definition and use of the physical supply chain networkassociated with an enterprise. The supply chain network is crucial tomany planning, execution, monitoring, and other enterprise solutioncomponents 6 supported using MDM system 4.

7. Sourcing Services

Sourcing services 18 g provide basic functions for accessing and usingelements of the MDM model that are relevant to sourcing solutioncomponents, such as a supplier relationship management solutioncomponent.

8. Activity Based Costing (ABC) Services

A number of useful measures may be associated with entities, such asitems where MDM system 4 is associated with a retail enterprise, thattraditionally have not been associated with an item catalog or similarconstruct. These measures may enable useful advanced analysis. Oneexample is cost and price data associated with items. Such data may beused for advanced pricing optimization and ABC analyses. In oneembodiment, MDM system 4 provides models to capture cost data, such ascost elements that when aggregated represent the total landed cost ofgoods. Included in these models are costs associated with activitiessuch as handling an item as it passes through points in the associatedsupply chain network. ABC services 18 h provide basic functions forhandling ABC data stored within and managed using MDM system 4.Moreover, data such as normalized demand profiles (or associations tosuch profiles) are examples of secondary attributes that MDM system 4may need to be accommodate.

9. Contract Services

In one embodiment, MDM system 4 does not inherently create or managecontracts for an example retail enterprise. However, MDM system 4preferably provides a repository for contract data as it relates toentities stored within MDM system 4 and provides a centralizeddistribution mechanism for contract data to appropriate enterprisesolution components 6. Contract services 18 i provide basic functionsfor inputting, associating, and distributing contract-related datarelated to core enterprise data residing within MDM system 4.

10. Bill of Materials (BOM) Services

For an example retail enterprise, BOM services 18 j provide basicfunctions for creating, managing, and visualizing BOMs for theenterprise. For example, a single actual BOM may be too atomic forplanning purposes, such that suitable aggregation of one or more actualBOMs into a representation appropriate for planning may be required tosupport a planning system associated with MDM system 4. MDM system 4 maystore such representations as reference data and make them available toplanning or other external operational systems as needed. MDM system 4may also automatically generate such representations, based on a MDM BOMmodel, to reduce or eliminate the need for manual evaluation andaggregation of individual actual BOMs to order to create suchrepresentations. BOM services 18 j preferably support the elements ofany appropriate MDM BOM model.

C. Data Layer

MDM system 4 is fundamentally concerned with the ability to create,manipulate, and extract data associated with the enterprise solution. Asdescribed above, data layer 20 provides the base data models andphysical representations for storing various types of enterprisereference data 22 for retrieval and use in connection with processes 14and associated services 18. In one embodiment, reference data 22 withindata layer 20 of MDM system 4 for an example retail enterprise mayinclude, without limitation: (1) master data 22 a; (2) metadata 22 b;(3) enterprise models 22 c; (4) parameter data 22 d; (5) attribute/traitdata 22 e; (6) event (calendar) data 22 f; (7) supply chain network data22 g; and (8) ABC data 22 h.

1. Master Data

Master data 22 a represents core configuration data associated withentities, such as items, locations, vendors, and customers for anexample retail enterprise. Many aspects of value chain managementgenerally, and most planning, execution, monitoring, or other enterprisesolution components 6 in particular, require reference data 22 regardingwhat items are sold, what locations sell the items, what vendors supplythe items, what customers purchase the items, and other fundamental dataelements on which all other enterprise data is built or to which allother enterprise data relates in some manner. MDM system 4 may extendthe traditional concept of master data with respect to such entities toaccommodate complex business workflows envisioned for an enterprisesolution. Although legacy masters, for example item masters, may captureattributes of items such as SKUs that indicate where the items fit intothe hierarchical structure of the enterprise data, there is no guaranteethat a legacy system could manipulate or even view such data in adimensional sense. In one embodiment, an item or other master for MDMsystem 4 is able to create, manipulate, navigate, view, and extract datain a dimensional way.

In one embodiment, an entity within a master data type represents anatomic member of that type, such as a particular item, a particularlocation, a particular vendor, or a particular customer. Attributes ofentities such as items, locations, and the like may have important roleswith respect to planning, execution, monitoring, and other enterprisesolution components 6. A first type of entity attribute is a physical orprimary attribute generally associated with inherent characteristics ofthe entity, such as size, weight, and color for an example item entity.Primary attributes may be very important, for example, in planningproduct assortments or solving logistics problems associated withshipping an order for an item. Primary attributes are reasonably staticand require no other context for meaning than the associated entityitself. A second type of entity attribute exists as a consequence of theuse of the entity within the enterprise, which may result in a definedrelationship of the entity to another entity or to an external metric.An example of such as attribute of an item might be the category orsub-category within the enterprise to which the item is assigned. Thistype of attribute, often referred to as a qualitative or secondaryattribute, may be very important for more advanced analytic techniquessuch as item grouping/clustering, customer focused marketing, andpromotions. In one embodiment, master data 22 a allows MDM system 4 tomanage both primary and secondary attributes of entities.

It may be important to distinguish between data considered to be masterdata 22 a and data considered to be attribute/trait reference data 22 edescribed below. As discussed above, master data 22 a may be reasonablystatic and may not change rapidly over time. For example, a color(primary attribute) of a particular shirt may not change within a seasonthe shirt is sold. Although the sub-category within the enterprise towhich the shirt is assigned (secondary attribute) may change, as aresult of a realignment for example, such changes will likely beinfrequent. In contrast, for example, attributes/trait data 22 e may beheavily used for targeted assortment and hence must capture dynamicbehaviors of customers. In addition, attributes/traits may themselveschange, with new attributes/traits being added as appropriate andexisting attributes/traits which are no longer valid being dropped asappropriate.

2. Metadata

Another form of reference data 22 that is inherent to the entity mastersdescribed above and is very important to many enterprise solutioncomponents 6 is enterprise metadata 22 b. In general, metadata 22 b isdata describing other data. In the context of MDM system 4, metadata 22b describes the structure of the data stored in and managed using MDMsystem 4. In general, metadata 22 b provides a description of thestructure of the dimensional view of master data 22 a. This descriptionfocuses on what dimensions exist, what levels describe the dimensioncoordinates, and what members exist and are associated with the levels.In addition, navigation constructs referred to as hierarchies may bedefined. For example, for an example retail enterprise, metadata 22 bmight include the various levels of the taxonomy of items and one ormore hierarchies for navigating through the various levels of thetaxonomy. In one embodiment, MDM system 4 captures metadata 22 b in aform that can be effectively replicated to downstream enterprisesolution components 6 that require consistency in the dimensional viewof master data 22 a. As described above in connection with metadatamaintenance services 18 b, MDM system 4 may manage the creation,manipulation, and deletion of metadata 22 b and provide for realignmentof master data 22 a (e.g. moving an item from a first category to asecond category) such that any realignment is properly reflected inmetadata 22 b.

3. Enterprise Models

Enterprise models 22 c represent organizational views of the roleswithin an enterprise. In one embodiment, enterprise models 22 c mayextend beyond the enterprise boundary to cover all organizationalelements of the value chain associated with the enterprise. Enterprisemodels 22 c may be important with respect to authentication andauthorization aspects of data access. Additionally, enterprise models 22c may provide for approval chain relationships important to businessprocess management.

4. Parameter Data

5. Attribute/Trait Data

6. Event (Calendar) Data

7. Supply Chain Network Data

8. Activity Based Costing (ABC) Data

III. MDM Logical Technical Architecture

FIG. 3 illustrates an example high level logical technical architecture30 for MDM system 4. In general, logical technical architecture 30represents a technology-centric view of MDM system 4 and specifieslogical elements of MDM system 4 that together may operate to providethe desired MDM solution. In one embodiment, logical technicalarchitecture 30 includes an MDM services framework 32 containing coreMDM services 34. MDM database 36 includes the core MDM reference datarepository. Certain services 34 may be applied to any classes ofreference data 22 to be modeled within the core MDM reference datarepository. Other services 34 may be tailored to particular classes ofreference data 22 modeled within the core MDM reference data repository.Other services 34 may generically support various security, data access,data staging, and other data management needs. Example services 34 aredescribed more fully below. Appropriate services 34 may access database36 using one or more appropriate data access links 38.

External operational systems 40 may access database 36 using one or moredata access layers 42. In one embodiment, an external operational system40 may access database 36 in connection with a business workflow using a“front side” data access layer 42 a, an associated “front” bus 44 abetween external operational system 40 and front side data access layer42 a, and an associated data interface 46 a between front side dataaccess layer 42 a and database 36. Front side data access layer 42 a istypically used to pass control data from external operational systems 40to MDM system 4 for controlling MDM operations and may be associatedwith application integration. One or more services 34 may accessfront-side data access layer 42 a using one or more suitable data accesslinks 48. An external operational system 40 may access database 36 usinga “back side” data access layer 42 b, an associated “back” bus 44 bbetween external operational system 40 and back side data access layer42 b, and an associated data interface 46 b between back side dataaccess layer 42 b and database 36. Back side data access layer 42 b istypically used for movement of reference data 22 to and from externaloperational systems 40 and may be associated with data integration.However, front side data access layer 42 a may also be used to movereference data 22 to and from external operational systems 40 whereappropriate, for example, where an external operational system 40requires particular reference data 22 in a particular message-based orother format.

A. Logical Data Services Architecture

FIG. 4 illustrates an example high level logical data servicesarchitecture 50 for MDM system 4. In one embodiment, data servicesarchitecture 50 includes primary layers: (1) a “front side” dataservices layer 52 a; (2) a physical data layer 54; and (3) a “back side”data services layer 52 b. Front side data services layer 52 a isassociated with front side data access layer 42 a, described above withreference to FIG. 3, and provides direct data access to internal MDMservices 34 that directly access the core MDM reference data repositorywithin database 36. For example, front side data services layer 52 a mayprovide direct access to database 36 for internal analytics or userinterface service queries. Physical data layer 54 includes database 36in which the core MDM reference data model resides. Back side dataservices layer 52 b is associated with back side data access layer 42 b,described above with reference to FIG. 3, and provides indirect dataaccess to external operational services 56 associated with externaloperational systems 40 that indirectly access the core MDM referencedata repository within database 36. For example, back side data serviceslayer 52 b may provide operational services with indirect access todatabase 36 through staging areas of database 36, staging areasassociated with external operational systems 40, and persistent datastores associated with external operational systems 40. In a physicaldeployment, each of the three primary layers of data servicesarchitecture 50 may be mapped to appropriate technology components.

Front side data services layer 52 a may be mapped to an appropriateobject-based services layer, such as Common Object Request BrokerArchitecture (CORBA) or JAVA 2 PLATFORM ENTERPRISE EDITION (J2EE),residing on an appropriate application server within an applicationserver layer (described below with reference to FIG. 9). In certainembodiments, front side data services layer 52 a may be more tightlycoupled to physical data layer 54 due to the necessity of anobject-to-relational translation layer as part of front side dataservices layer 52 a.

Database 36 within physical data layer 54 may be implemented as arelational database. Database 36 may be modeled and managed in a numberof ways, one of which may be selected for a particular deployment. Inone embodiment, object relational database management technology may beused, although this approach is typically subject to performance risks.With this approach, the core MDM reference data model may be mapped toexisting services 34 using a suitable object relational mapping layer.In an alternative embodiment, for improved performance or other reasons,a fixed data model relational database with a light access layer may beused. The light access layer would provide persistent objects tailoredto the fixed and optimized physical schema of the relational databaserather than driving the physical schema through an object relationalmapping layer. With this approach, new services 34 may be mapped to anexisting core MDM reference data model.

Although a single core MDM reference data repository within a singledatabase 36 is primarily described herein for convenience, the presentinvention contemplates any number of core MDM reference datarepositories within any number of databases 36 according to particularneeds. However, all core MDM reference data repositories within alldatabases 36 are subject to centralized data management associated witha single MDM system 4 and preferably appear to both internal MDMservices 34 and external operational services 56 as a single core MDMreference data repository.

Back side data services layer 52 b is preferably optimized forpotentially large data synchronization and replication operations,preferably incorporating net change techniques, efficient storeprocedure techniques, and an object-based control layer. Furthermore,since back side data services layer 52 b maps to planning, execution,monitoring, or other enterprise solution components 6 for which datamovements and associated mappings (i-e. transformations) must remainreasonably fixed over time, the core MDM reference data model shouldalso be reasonably fixed over time.

B. Logical Data Repository Architecture

FIG. 5 illustrates an example high level logical architecture 70 ofdatabase 36. In one embodiment, database 36 incorporates a consistentdimensional modeling framework imposed on a model supporting apersistence management service, which is described more fully below.This preferably allows services framework 32 to manage reference data 22within database 36 in a manner that is consistent with establisheddimensional views of reference data 22. Where MDM system 4 does notphysically contain all reference data 22, reference data 22 that is notphysically contained in MDM system 4 preferably appears as if it isphysically contained in MDM system 4. Database 36 includes a manageddata area 72 containing reference data 22, at least some of which may bemanaged remotely from MDM system 4. Managed data area 72 provides thecore MDM reference data repository for reference data 22. Database 36may also include a cached data area 74 containing cached data 76representing reference data 22 that has been extracted from managed dataarea 72, processed according to the needs of one or more elements of MDMsystem 4 using a data management framework 78, and is re-inserted inmanaged data area 72 as reference data 22 once processing is complete.For example, data management framework 78 may provide the processcontroller within business process toolkit 34 a, UI services 34 d, orany other suitable element of MDM system 4 with operational access tocached data 76.

Reference data 22 stored within MDM system 4 has an assigned stateconsistent with its use. In one embodiment, in association with datamanagement framework 78, cached data area 74 provides a mechanism tohold a copy of reference data 22 for manipulation while the state′ ofreference data 22 in managed data area 72 is maintained as locked forread only access until the manipulation process has completed. Once acopy of reference data 22 is being held as cached data 76 within cacheddata area 74 during the manipulation process, the manipulation processsees only the state of cached data 76 within cached data area 74, whileother processes, services, and systems associated with MDM system 4 seethe true state of reference data 22 within managed data area 72 ratherthan an intermediate state reflecting the still incomplete manipulationprocess.

Database 36 may also include an operational access area 80 providing oneor more external operational systems 40 with access to reference data 22within managed data area 72. Where MDM system 4 is associated with anexample retail enterprise, external operational systems 40 may includeexternal enterprises such as manufacturers, distributors, and vendors ofitems associated with enterprise. External operational systems 40 mayalso include planning, execution, monitoring, and other enterprisesolution components 6 within the enterprise but external to MDM system4. Operational access area 80 may containing a master copy 82 of anLightweight Directory Access Protocol (LDAP) repository used to provideauthentication and authorization services as described more fully below.Operational access area 80 may also contain inbound and outbound stagingareas 66 and 68, respectively, for data that is inbound from andoutbound to, respectively, external operational systems 40.

C. Information Sharing Architecture

In one embodiment, data may enter MDM system 4 from any appropriatesource and may leave MDM system 4 for any appropriate target. Unlessreference data 22 stored within the core MDM reference data repositorycan be readily made available to external operational systems 40,storing reference data 22 within the core MDM reference data repositorymay provide little value to the enterprise. Conversely, there may beother data residing within portions of the enterprise that needs to bedistributed to other portions of the enterprise through MDM system 4.FIG. 6 illustrates an example information sharing architecture 90 forMDM system 4. In one embodiment, database 36 may be optimized formanagement of reference data 22 rather than for speed of data input ordata output. Accordingly, a staging strategy may be employed to minimizedata transfer times to and from external operational systems 40.

As described above, inbound data may be received from one or more datasources 92 for storage in the core MDM reference data repository ofmanaged data area 72. Data sources 92 may include persistent data storesassociated with external enterprises 40 a, such as manufacturers,distributors, vendors, and customers where MDM system 4 is associatedwith an example retail enterprise. Data sources 92 may also includeoperational staging data stores associated with planning, execution,monitoring, or other enterprise solution components 6. The inbound datais first moved into inbound staging tables 94 of inbound staging area84, then into core MDM tables 96 within the core MDM reference datarepository of managed data area 72 as reference data 22. Data cleansing,validation, transformation, or other processing may occur, whereappropriate, during the movement of data from inbound staging area 84 tothe core MDM reference data repository managed data area 72. Forexample, it may be very important that reference data 22 stored withinthe core MDM reference data repository and made available to externaloperations systems 40 is considered clean, such data cleansing inconnection with loading of inbound data.

As described above, outbound data may be provided to one or more datatargets 98, such as persistent data stores associated with externalenterprises 40 a or operational staging data stores associated withplanning, execution, monitoring, or other external enterprise solutioncomponents 6. Outbound data being distributed using MDM system 4 withoutbeing stored in the core MDM reference data repository may be sent frominbound staging tables 94 of inbound staging area 84 to outbound stagingtables 100 a of uncoupled outbound staging area 86 a, then out to datatargets 98. Similarly, outbound reference data 22 in the core MDMreference data repository of managed data area 72 may be moved out ofcore MDM tables 96 of managed data area 72 to outbound staging tables100 b of coupled outbound staging area 86 b, then out to data targets98. Reference data 22 stored within core MDM tables 96 may besubstantially continuously synchronized with the outbound data inoutbound staging tables 100, such that at any point in time an accuratesnapshot of reference data 22 is available within outbound staging area86. Synchronization of reference data with operational data may beimportant, for example, to help ensure that planning based uponoperational data is not performed for an entity that no longer existswithin the enterprise as reflected in reference data 22. Datatransformation or other processing may occur, where appropriate, duringthe movement of reference data 22 from the core MDM reference datarepository of managed data area 72 to outbound staging area 86.

D. MDM Services Framework

Referring again to FIG. 3, in one embodiment, services framework 32 mayprovide services 34 organized into the following groups, withoutlimitation: (1) business process toolkit 34 a, (2) security services 34b, (3) general services 34 c, (4) user interface services 34 d, (5) dataaccess services 34 e, and (6) data staging services 34 f.

1. Business Process Toolkit

Business process toolkit 34 a may be provided using a correspondingsubsystem within services framework 32 that provides for management ofMDM models, processes, and associated business rules. Automatedprocesses associated with this subsystem may be used to implement modelchanges associated with physical deployment of MDM system 4. In oneembodiment, business process toolkit 34 a may include, withoutlimitation: (1) a MDM studio, (2) a MDM model library, (3) a businessrules management service, (4) a process controller, and (5) a MDMstructure update service.

a. MDM Studio & MDM Model Library

FIG. 7 illustrates an example MDM studio 110 and an associated MDM modellibrary 112 containing one or more MDM models 114 appropriate for MDMsystem 4. MDM studio 110 may provide services to model the structure ofMDM system 4 and its components, for example, for purposes ofconstructing MDM system 4 or for purposes of extending or otherwiseupdating MDM system 4. MDM studio 110 may provide support for one ormore graphical modeling user interfaces. Modeling of MDM system 4 mayinclude, for example, modeling structural aspects of the core MDMreference data repository within managed data area 72 of database 36,modeling the structure of staging areas 66 and 68 of database 36, andmodeling appropriate process workflows. MDM studio 110 may providesupport both for initial construction of MDM models 114 and laterextension or other updating of MDM models 114. In one embodiment, MDMmodels 114 include, without limitation: (1) MDM process model 114 a, (2)MDM document model 114 b, (3) MDM forms model 114 c, (4) MDM referencedata model 114 d, and (5) MDM staging data model 114 e.

(1) MDM Process Model

Process models 114 a describe the processes 14 to be used for managingreference data 22 stored within the core MDM reference data repositorywithin database 36. In one embodiment, for a particular process 14, thecorresponding process model 114 a describes the flow of tasks to beperformed on reference data 22 in connection with process 14, particularservices 18 associated with these tasks, and one or more particularprocess engines responsible for execution of process 14. For serviceoriented tasks, descriptions may utilize Web Services DescriptionLanguage (WSDL) protocols. Each process 14 may represent one or moreuser interface task flows, enterprise solution component task flows,inter-enterprise process flows, or any other appropriate processes ortask flows. Process model 114 a may specify allocation of each process14 to a process controller, user interface controller, orenterprise-level workflow controller. Process model 114 a may alsoprovide for graphical or other simulation of processes 14.

(2) MDM Document Model

Document model 114 b provides the metadata for MDM documents that areutilized in connection with processes 14. In one embodiment, MDMdocuments represent external cached representations of specific metadataelements within the underlying reference data model 114 d.

(3) MDM Forms Model

Forms model 114 c provides metadata describing forms associated withobjects within reference data model 114 d. Forms may be important forefficient extraction of metadata elements from reference data model 114d and may be analogous to database views.

(4) MDM Reference Data Model

Reference data model 114 d represents the metadata describing referencedata 22 stored within the core MDM reference data repository. This isthe lowest level metadata representation contained within model library112. In one embodiment, reference data model 114 d may be an enterprisemeta-model in Extensible Markup Language (XML) Software Description(XSD) format, which may separate instance data from metadata in a mannerdesirable for management and which back side data access layer 42 b mayread directly from model library 112. It may be important to synchronizechanges to reference data model 114 d with any higher level constructs,such as forms model 114 c or document model 114 b. Synchronization ofmodels 114 may be automatic or, if appropriate, studio 110 may flag theneed for changes and direct an administrative user to assist insynchronizing models 114.

A generic reference data model for reference data 22 to be stored withinthe core MDM reference data repository may be constructed to represent asynthesis of all applicable data elements, such as all data elementsassociated with enterprises in the retail industry for example, and maybe viewed as a superset of reference data models 114 d to be used inactual deployments of MDM system 4. The generic reference data model,and all reference data models 114 d ultimately derived from the genericreference data model, should be constructed for consistency andefficient management of reference data 22. In one embodiment, thegeneric reference data model may be captured as a document in anannotated RATIONAL ROSE object model.

(5) MDM Staging Data Model

Staging data model 114 e represents metadata describing the structure ofinbound and outbound staging tables 94 and 78, respectively, and alsothe mapping between reference data model 114 d and the staging tablerepresentation of the data within inbound and outbound staging tables 94and 78, respectively. Reference data model 114 d may be a normalizeddata model derived from a generic reference data model as describedabove. However, inbound data may reflect arbitrary schema that areinconsistent with reference data model 114 d. For inbound data,appropriate mappings (i.e. transformations) of reference data model 114d to source data models, such as an inbound staging data model 114 erepresenting an arbitrary input data format for an external operationalsystem 40, may be performed as inbound data is being stored in the coreMDM reference data repository. Similarly, outbound data may need to bede-normalized for consumption as operational data. For outbound data,appropriate mappings (i.e. transformations) of reference data model 114d to target data models, such as an outbound staging data model 114 erepresenting a flat output data format for an external operationalsystem 40, may be performed as reference data is being moved out of thecore MDM reference data repository.

b. Business Rules Management Service

Referring again to FIG. 3, the business rules management service mayprovide for creation and maintenance of business rule elementsassociated with services 18, such as import validation rules, stagingtransformation rules, and general consistency rules associated with MDMsystem 4. The business rules management service may provide forruntime-script-based rules or for association of design-time rulesobjects with MDM process workflows.

c. Process Controller

The process controller may represent a run-time process workflowcontroller for MDM system 4. As described above, process model 114 a mayspecify allocation of one or more processes 14 to the processcontroller, a user interface controller, or an enterprise-level workflowcontroller. In one embodiment, the process controller operates incooperation with any such user interface controller and any suchenterprise-level workflow controller.

d. MDM Structure Update Service

In one embodiment, MDM system 4 provides a mechanism to model itsstructure and a mechanism to automate a process to realize an extensionof that model in a physical deployment. The structure update service mayprovide for automated implementation of a model 114 that is created orchanged during the modeling process. The structure update service may beparticularly important with respect to the structure of inbound andoutbound staging areas 66 and 68, respectively. It may be necessary toinitially specify staging data model 114 e, the reference model tostaging area structure. In addition, it may be necessary to generateappropriate Structured Query language (SQL) or changes to SQL tomaintain the state of staging areas 66 and 68 relative to staging datamodel 114 e. Without automation of these tasks using the structureupdate service, maintaining coordination of various elements of MDMsystem 4 would be a very intensive manual task. The structure updateservice may also provide for updating staging data model 114 e and othermodels 114, along with associated SQL, in response to updates providedwith enterprise solution components 6. Such structure updates may bedriven according to update description script documents providinginformation necessary for the structure update to automatically execute.

2. Security Services

Naturally, only users with appropriate access should be permitted toview or manipulate reference data 22 within MDM system 4. Securityservices 34 b may be provided using a corresponding subsystem withinservices framework 32 designed to fulfill two primary responsibilities.The first responsibility is to control access to MDM system 4 itself.The second responsibility is to manage the structure of the securitymodel as applied to enterprise solution components 6. For thisresponsibility, services are provided to manage the security contextthat all enterprise solution components 6 will utilize, for example,through an LDAP repository whose master copy 82 resides withinoperational access area 80 of database 36. Security services 34 b mayinclude, without limitation: (1) authentication services, and (2)authorization services.

a. Authentication

Authentication services provide initial log-in security with respect toenterprise solution components 6. Authentication is preferably based onan organizational model for the enterprise to provide a single log-insecurity context for all enterprise solution components 6.

b. Authorization

Authorization services provide layered, granular access to specificservices 18 or reference data 22 for an authenticated user.Authorization may be provided at two levels. The first level (Level 1)deals with access to enterprise solution components 6 represented byspecific applications or high level groups of services 18. The secondlevel (Level 2) deals with access to specific functions within anenterprise solution component 6. Field level authorization may behandled by particular enterprise solution components 6 themselves asappropriate. In the case of MDM system 4 itself, any requiredauthorization above Level 2 (i.e. Level 3 and higher) may need to beprovided within MDM system 4.

3. General Services

General services 34 c may be provided using a corresponding subsystemwithin services framework 32 and may include, without limitation: (1) achange management service; (2) a lifecycle management service; (2) agroup management service; and (4) an analytics and reporting service.

a. Change Management

The change management services provides an audit trail for changes madeto MDM system 4. For example, information may be kept regarding who madea change, at what time the change was made, and perhaps the value thatwas changed. The audit trail for changes should preferably beimplemented in such a fashion that the mechanism can be turned off forinformation not requiring change management or for changes prior toconfiguration control, such as changes associated with initial setup ofdata elements. Logical grouping of reference data 22 may be importantfor many data management aspects, such as retrieving reference data 22and making changes to reference data 22. Therefore, in terms ofgranularity, in one embodiment change management is group-based withoverrides at the group member level.

b. Lifecycle Management

As described above, reference data 22 stored within MDM system 4 has anassigned state consistent with its use. The lifecycle management serviceallows for defining a lifecycle that describes the possible states fordata elements, as well as a mechanism for managing the movement of datafrom one lifecycle state to another.

c. Group Management

Given the vast scope and scale of data that may potentially residewithin MDM system 4, it is preferable that the overall strategy for datamanagement be based on logical groups of data rather than individualdata elements. Logical grouping of reference data 22 may be importantfor many data management aspects, such as retrieving reference data 22and making changes to reference data 22. Although single entities may bemanipulated, many updates will typically occur with respect to groups ofentities. In one embodiment, the group aspect of data manipulation isbuilt in from the foundation of MDM system 4.

d. Analytics and Reporting

The health and status of a large data repository, such as the core MDMreference data repository within database 36, is critical. The analyticsand reporting service provides knowledge concerning what reference data22 is stored within the core MDM reference data repository and the stateof various system elements of MDM system 4. Although the types ofanalysis and associated reports will be specific to MDM system 4,general analysis and reporting tools may be used where appropriate.Analytics may extend to a broad range of activities supported directlyby this service or indirectly through management by this service.Analytics may include clustering services for attributes/traits,decision support activities relating to entity data stored within thecore MDM reference data repository, management of parameter computationsuch as coordinating parameter computation using an external engine,updating parameters such as lead times for items at particularlocations, and any other suitable analytics. Reports may include changelog activity, history traces for specific entities or groups ofentities, reports on production parameter sets including time-phasedsets, calendar examination and reconciliation, reports on new entities(such as new items) entered into the core MDM reference data repositoryand dying entities (such as items) removed from the core MDM referencedata repository, and any other suitable reports.

4. User Interface Services

5. Data Access Services

Data access services 34 e may be provided using a correspondingsubsystem within services framework 32 to provide a key interfacebetween user interface layers, data management business rules, and theunderlying core MDM reference data repository within database 36. Dataaccess services 34 e may be included within data management framework 78described above with reference to FIG. 5. Since in one embodiment thepredominant view of reference data 22 is object-based, data accessservices 34 e may support a persistent mapping to underlying datastructures within database 36. Accordingly, in one embodiment, dataaccess services 34 e may incorporate the concept of a data cache, suchas cached data area 74 of database 36 described above, that provides amechanism to hold a copy of reference data 22 in cached data area 74 formanipulation while maintaining the state of reference data 22 in thecore MDM reference data repository of managed data area 72 as locked forread only access until the manipulation process has completed. Once acopy of reference data 22 is being held as cached data 76 within cacheddata area 74 during the manipulation process, the manipulation processsees only the state of cached data 76 within cached data area 74, whileother processes, services, and systems associated with MDM system 4 seethe true state of reference data 22 within managed data area 72 ratherthan an intermediate state reflecting the still incomplete manipulationprocess. Data access services 34 e may include, without limitation: (1)a persistence management service; and (2) a data access layer service.

a. Persistence Management

The persistence management service provides the logical mapping betweenthe user view of reference data 22 and the underlying persistent objectmodel associated with reference data 22. The service provides formanaging the creation, update, and deletion of model instances,including appropriate memory-level caching of persistent objects.

b. Data Access Layer

The data access layer service provides the link between the logicalobject model associated with reference data 22 and the physicalinstances of relational core MDM tables 96 in which the persistentobjects are held as reference data 22. The separation of the persistencelayer from a particular physical mapping layer allows for multiplephysical targets, which is especially useful when a distributed physicaldata model is required (e.g., in certain cases of parametermaintenance).

6. Data Staging Services

Data staging services 34 e may be provided using a correspondingsubsystem within services framework 32, primarily to providesynchronization of inbound and outbound staging areas 66 and 68,respectively, with managed data area 72 of database 36. Data stagingservices 34 e may include, without limitation: (1) a data importservice; (2) a validation service; and (3) a syndication service.

a. Data Import

The data import service provides functions for moving data from externalsources into database 36. For example, the data import service might beused to move existing master data into database 36 for storage and laterredistribution to one or more planning, execution, monitoring, or otherenterprise solution components 6. Importing data includes moving theinbound data into inbound staging area 84, validating and transformingthe inbound data where appropriate, and moving the inbound data frominbound staging area 84 into the core MDM reference data repository ofmanaged data area 72 as reference data 22.

b. Validation

The validation service allows predefined, as well as user-defined,validation rules to be applied to inbound data prior to insertion intodatabase 36. Validation rules may include basic value type rules,referential integrity rules, enterprise-specific business rules, or anyother suitable rule. In one embodiment, validation is selectable suchthat higher levels of validation may be used when an inbound data set is“dirty,” requiring more stringent validation, and lower levels ofvalidation may be used when an inbound data set is “clean,” requiringless stringent validation.

c. Syndication

The syndication service, which essentially exports data from database 36to planning, execution, monitoring, or other enterprise solutioncomponents 6, may have two primary elements. The first element providesfunctions for synchronization of core MDM tables 96 within managed dataarea 72 with outbound staging tables 100 within outbound staging area86, such that a valid snapshot of reference data 22 exists at all timeswithin outbound staging tables 100, consistent with update transactionboundaries. The second element provides functions for schedule-based ordemand-based movement of data from outbound staging tables 100 to atarget enterprise solution component 6.

IV. MDM Use Model

FIG. 8 illustrates an example MDM use model 130 for MDM system 4. Ingeneral, use model 130 describes how MDM system 4 will be used in termsof where data is stored and how the data is accessed. In one embodiment,the external operational systems 40 that interact with MDM system 4 viewMDM system 4 as a reference data repository, not as an operational datasource. Accordingly, reference data 22 within core MDM reference datarepository 132 may be synchronized and replicated to local persistentstores 134 of external operational systems 40 through appropriateexternal access services 136 operating in association with one or bothdata access layers 42. Internal access services 138 associated withmanaging reference data 22 within MDM system 4 may have direct access toreference data 22 within core MDM reference data repository 132. Incontrast, operational services 140 of external operational systems 40,which are not associated with managing reference data 22 within MDMsystem 4, may only access data within the associated persistent stores134, never directly accessing reference data 22 within core MDMreference data repository 132. Thus, in essence, MDM system 4 may act asa secure system of record that is optimized in architecture and designfor management of reference data 22 rather than operational use ofreference data 22. Consuming services other than those related tomanaging reference data 22 are not permitted to directly accessreference data 22.

In one embodiment, key metrics to be considered in designing a physicalarchitecture in accordance with use model 130 may include, withoutlimitation: (1) throughput performance; (2) query performance; (3)configuration flexibility; and (4) scale. Each of these metrics isdiscussed below in relation to appropriate physical characteristics ofan implementation of MDM system 4.

A. Throughput Performance

The primary use model for MDM system 4 features a centralized masterrepository, core MDM reference data repository 132 of managed data area72 of database 36, for the core enterprise data, reference data 22. Inone embodiment, a goal is to shield core MDM reference data repository132 from operational loading while allowing for optimal design ofexternal operational systems 40 that use reference data 22 in anoperational mode. Accordingly, as described more fully above, use model130 calls for synchronizing and replicating reference data 22 into localpersistent stores 134 of external operational systems 40 that usereference data 22. This implies a physical architecture and design thatfacilitate outbound throughput performance for moving reference data 22from core MDM reference data repository 132 to target persistent stores134. If reference data 22 is being moved in quantity from externaloperation systems 40 into MDM system 4, then the physical architectureand design should preferably also support inbound throughputperformance. A primary design criterion following from the above is thatphysical data layer 54 should provide for as efficient access toreference data 22 as possible. It may be desirable to consider anyindirection layer that resides between core MDM tables 96 containingreference data 22, which may have a relational table structure, and theexterior representation of reference data 22, which may be an objectrepresentation.

B. Query Performance

The context for query performance is that of constructing views ofreference data 22 for the MDM user interface or an analytics serviceinternal to MDM system 4, such as the analytics and reporting servicedescribed above with reference to FIG. 3. Such user interface andanalytics service queries are likely to be more filter-driven, lookingfor particular subsets of reference data 22 within a much larger rowcontext, than any SQL or other queries associated with the bulk exportof reference data 22 discussed above with respect to throughput. Thestructure of physical data layer 54 and the associated data access layerservice should be designed to handle potentially large numbers ofcomplex queries in a timely manner. Return of large and small queryresult row sets should be efficient independent of the target service(e.g., the user interface). Design criteria for query performance mayinclude low mean query response times at the database level, sufficientperformance under inbound loading involving a large number of inboundqueries, and minimal latency in the associated data access layerservice.

C. Configuration Flexibility

Configuration flexibility may be examined from both the user view andthe solution view. With respect to the user view, reference data 22contained in core MDM reference data repository 132 needs to be mappedto a particular data view that the enterprise requires. With respect tothe solution view, where the core metrics are typically performance inreplication and query performance, configuration flexibility may be lesscritical if not counter to those metrics. In general, it would be unwiseto change reference data model 114 d for each enterprise deployment,since that would imply reconfiguration of all interfaces from core MDMreference data repository 132 to local persistent stores 134 of externaloperational systems 40. A design criterion for configuration flexibilityis that reference data model 114 d should be stable from deployment todeployment and should represent a superset of anticipated reference data22 for any enterprise. Attainment of this state may be evolutionary overseveral deployments, but should be smoothly accomplished in a relativelyshort period of time without significant model redesign. If a user viewmapping configuration is required, it should preferably be at theoutermost layers of the design (i.e. close to the user interface ratherthan interior to data structures of core MDM reference data repository132).

D. Scalability

Core MDM reference data repository 132 may hold vast amounts ofreference data 22, particularly where MDM system 4 is associated with anexample retail enterprise having very large numbers of items, locations,or other entities. If attribute/trait data 22 e is utilized, whereseveral hundred trait attributes per entity may be common, the potentialfor vast amounts of reference data 22 is even higher. Thesecharacteristics may effectively lead to large table row counts, complexrelational joins, and the need for a dimension framework for referencedata 22. A design criterion for scalability, which is also related toboth throughput and query performance, is the ability to efficientlyhandle large row sets both when querying into the sets and when movingthe sets. These type of efficiencies generally come from well-designedand well-tuned relational tables specifically engineered forperformance-related metrics. A corollary is that the design shouldpreferably be capable of utilizing parallel database technology ifpossibly required to sufficiently scale in the enterprise environment.If the design cannot utilize parallel database technology, then theoption is lost when attempting to boost performance through deploymentconfiguration.

V. User Interface Architecture

There are several drivers for the architecture and design of a userinterface for MDM system 4. A first driver is the dual types of users ofMDM system 4; the administrative role user and the process participantrole user. The first classification of user role is concerned primarilywith the administration of enterprise configuration informationcontained within MDM system 4, as well as the associated MDM models 114,which are realized physically in database 36. The second classificationof user role is more concerned with viewing and entering informationassociated with processes 14, such as new item introduction for example.A modeling studio style interface may be more important to theadministrative role user, while well-designed view and entry screensequences may be more important to the process participant role user.User interface architecture and design requirements may be broken downalong these or other suitable lines. A second driver is the flexibilitythat is inherent in the MDM architecture. In one embodiment, bothreference data model 114 d and staging data model 114 e may be alteredat the time of deployment. This provides flexibility for MDM system 4 toaccommodate idiosyncrasies of the enterprise. Correspondingly, the userinterface architecture preferably accommodates these flexible models.For example, if a field is added or deleted within reference data model114 d or staging data model 114 e, a corresponding entry screen mayaccordingly adapt dynamically to the model change without the need forreprogramming.

VI. MDM Physical Architecture

FIG. 9 illustrates an example high level physical architecture 150 forMDM system 4, which may be loosely mapped to logical businessarchitecture 10 described above with reference to FIG. 2 and logicaltechnical architecture 30 described above with reference to FIG. 3.

In one embodiment, MDM system 4 includes a web server 152, a MDMapplication server layer 154, an infrastructure services applicationserver layer 156, and a MDM database layer 158. Using a web browser orotherwise, a user associated with MDM system 4 may send a HypertextTransport Protocol (HTTP) or other request to web server 152 to performan appropriate operation. Web server 152 may communicate the request toone or more appropriate application servers within application serverlayer 154 to invoke one or more suitable applications 160. Applicationserver layer 154 may include one or more application servers supportingengines 160 a that provide process and service functions of MDM system4, supporting the MDM user interface 160 b, and supporting othersuitable applications 160. Infrastructure services application serverlayer 156 may include one or more application servers supporting frontside data access layer 42 a, back side data access layer 42 b, and asuitable enterprise-level workflow engine 162 that provides process andservice functions associated with data access layers 42. For example, inone particular embodiment, front side data access layer 42 a may beimplemented using a WEBMETHODS ENTERPRISE SERVER product, back side dataaccess layer 42 b may be implemented in part using an INFORMATICAPOWERCENTER product with an integrated Extract-Transform-Load (ETL)tool, and enterprise-level workflow engine 162 may be implemented usinga WEBMETHODS BUSINESS INTEGRATOR product.

In one embodiment, implementation of processes 14 may be shared betweenenterprise-level workflow engine 162 of application server layer 156 andapplications 160 of application server layer 154. Services 12 andassociated services 34 may be provided primarily using applicationserver layer 154. Database layer 158 contains the actual physical datamodels 114, such as reference data model 114 d and staging data model114 e described above with reference to FIG. 7, with associated dataservices provided either at database layer 8 or application server layer154.

VII. Example New Item Introduction Process

FIG. 10 illustrates an example new item introduction process 14 providedwithin MDM system 4. Although introduction of a new item entity forretail and associated vendor enterprises is described as an example, thepresent invention contemplates analogous or other introduction of anysuitable new entity for any suitable enterprise, whether or notspecifically described herein.

New item introduction is a very common and integral practice for dynamicvalue chain partners such as retailers and finished goods vendors. Thefrequency of new items being introduced to a retailer assortment mayvary from one to one thousand each week, depending upon the retailsegment and other factors. New item introduction may be the mostimportant phase in the life cycle of an item. This process hastraditionally been highly paper intensive and has impeded the ability ofretailers and vendors to introduce items on a dynamic (i.e. day-today)basis, since there are thousands of variables, attributes, and otherfactors that may need to be considered in introducing a new item at theretailer shelf, from pricing to shelf-level execution. There is abusiness need for retailers to automate significant portions of the newitem introduction process, and to streamline integration with planning,execution, monitoring, and other enterprise component solutions, tointroduce new items with a shorter time-to-market, generate customerinterest, and gain market share. In one embodiment, with new itemintroduction process 14, MDM system 4 incorporates an embedded businessworkflow for new item introduction that enables an example retailenterprise to introduce a new item more quickly, more easily, with moreflexibility, and with more streamlined integration with planning,execution, monitoring, or other enterprise solution components 6 thanwith previous techniques.

A new item may be introduced in a number of different ways. For example,a vendor may introduce the new item to a retailer, a retailer mayintroduce the new item through item design (i.e. for private label), ora retailer and vendor may jointly decide to introduce the new item.Although there may be slight variations in these three methods of newitem introduction, since this example will focus on the workflowsinternal to the retailer, this description will include details of newitem introduction from a generic perspective. That is, the describedworkflows are generic in that they outline the processes that theretailer may go through, irrespective of whether the retailer introducesthe new item, the vendor introduces the new item, or the retailer andvendor jointly introduce the new item. These workflows may also beapplicable across all retailer formats (e.g., mass merchant, departmentstore, etc.) and all merchandise segments (hardlines, grocery,softlines, etc.).

As illustrated in FIG. 10, in one embodiment there are two major aspectsof new item introduction process 14: (1) a first sub-process 170involving introduction, review, acceptance, and rejection of the newitem, which may be analogized to the conception of a child; and (2) asecond sub-process 172 involving creation of the new item within theretailer for initiating merchandising, replenishment, and supply chainplanning and execution functions on the new item to make the new itemavailable at the shelf for sale to the customer, which may be analogizedto the birth of the child. First sub-process 170 may include, withoutlimitation: a vendor introduction component 174 (where the vendor isintroducing the new item), a retailer review component 176; a retailerrejection/modification component 178; a retailer approval component 180;and a vendor/retailer agreement finalization component 182. Secondsubprocess 172 may include a vendor/retailer keying component 184, inwhich the vendor or retailer creates one or more appropriate masters forthe new item within database 36. Such masters may include, for example,an item master 186, an item-location master 188, and a vendor-itemmaster 190. After creation and storage of masters for the new itemaccording to execution of vendor/retailer keying component 184, legacysystems 192 and associated production databases 194 of the retailer orvendor may receive and recognize the new item for merchandising,replenishment, and supply chain planning and execution functions.

There may be many potential benefits of providing wholly or partiallyautomated processes 14 for new item introduction, entry, creation, andmaintenance. For example, automation of the new item introductionprocess may provide one or more of the following benefits, withoutlimitation: (1) providing the retailer with the ability to merchandiseand incorporate a new item into its assortments more quickly, therebymaking the new item available to customers more quickly than itscompetitors; (2) as a result of a shorter time-to-market for new items,the retailer may considerably improve its chances of increasing salesand market share; (3) reduced labor costs and paper-flow within andacross various retail functions; (4) reducing or eliminating thepossibility of keying errors, thereby reducing the potential for humanerror; (5) providing tighter and more streamlined integration of the newitem introduction process with planning, execution, monitoring, or otherenterprise solution components 6, leading to better placement andreplenishment of merchandise; and (6) efficiencies in planning andexecution achieved through streamlined integration with new itemintroduction may be effectively leveraged to provide the lowestshelf-landed cost to the end-customer. With respect to tighter and morestreamlined integration, examples may include, without limitation: (1)data from a vendor's quote associated with a new item may beautomatically filled in for the retailer, no longer needing to bemanually keyed in to finalize a contract with respect to the new item;(2) Universal Product Code (UPC) number may be automatically created fora new item once the new item has been created, no longer needing to bemanually keyed in; (3) a retailer legacy system may be automaticallychecked to verify that a UPC number for a new item is associated with aretailer product number, no longer needing to be manually verified; and(4) in association with a merchandise planning system or otherenterprise solution component 6, a product number for a new product maybe automatically filled in for creation of a product assortmentincorporating a new item, no longer needing to be manually keyed in.

New item introduction process 14 illustrated in FIG. 10 may be describedin more detail, from introduction of the new item by the vendor throughmaintenance of the item by the retailer in its systems. In oneembodiment, new item introduction, entry, creation, and maintenanceassociated with new item introduction process 14 within an exampleretailer may be broken down into the following primary sub-processes,without limitation: (1) an initiation sub-process; (2) a preliminaryplanning sub-process; (3) an item entry, approval, initial forecastestimation, and replenishment initiation sub-process; (4) an item setup,creation, activation, and initial replenishment sub-process; (5) an itemmerchandising and shelf execution setup sub-process; (6) an itemforecast entry and replenishment sub-process; (7) an order managementand collaboration sub-process; (8) inbound (vendor-to-retailer) andoutbound (retailer-to-location) supply chain planning and executionsub-processes; (9) an item maintenance sub-process; and (10) anexceptions handling and management sub-process.

Although the present invention has been described with severalembodiments, a plethora of changes, substitutions, variations,alterations, and modifications may be suggested to one skilled in theart, and it is intended that the invention encompass all such changes,substitutions, variations, alterations, and modifications as fall withinthe spirit and scope of the appended claims.

What is claimed is:
 1. A system of centrally managing managed data of anenterprise, comprising: an infrastructure services layer tangiblyembodied on a non-transitory computer-readable storage media and coupledwith a centralized master repository, the infrastructure services layerproviding messaging between the centralized master repository and one ormore external operational systems, the external operational systemspermitted indirect access to managed data of the enterprise stored inthe centralized master repository, the infrastructure services layerfurther providing mapping between the centralized master repository andthe one or more external operational systems; a database comprising acached data area comprising cached data representing managed data of theenterprise extracted from a managed data area in response to aprocessing request from one or more internal services and re-insertedinto the managed data area following processing from one or moreinternal services, one or more of the internal services directlyaccessing the managed data of the enterprise stored in the centralizedmaster repository; and an inbound staging area comprising one or moreinbound staging tables and the managed data area comprises one or morecore master data management (MDM) tables, wherein inbound data istransferred from the one or more data sources to the one or more inboundstaging tables before the one or more core MDM tables; one or more datatargets, wherein outbound data is provided to the one or more datatargets; and when the outbound data is not sourced from the centralizedmaster repository, transferring the outbound data from the one or moreinbound staging tables to one or more outbound staging tables of anuncoupled outbound staging area before the one or more data targets;when the outbound data is sourced from the centralized masterrepository, transferring the outbound from the one or more core MDMtables to one or more outbound staging tables of a coupled outboundstaging area before the one or more data targets; synchronizing datawithin the one or more core MDM tables with the outbound data in the oneor more outbound staging tables of the coupled outbound staging area andthe uncoupled outbound staging area; and wherein the managed data areastores the managed data of an enterprise as cached data in anintermediate state according to a manipulation process, the managed dataof the enterprise is maintained as locked in its true state for readonly access until completion of the manipulation process, outputting theintermediate state of the cached data related to the managed data of theenterprise to an entity of the enterprise.
 2. The system of claim 1,wherein during transfer of the inbound data from the one or more inboundstaging tables to the one or more core MDM tables, the internal servicesframework performs one or more of cleansing, validation, transformation,and processing of the inbound data.
 3. The system of claim 2, furthercomprising: a syndication service configured to synchronize the inboundstaging area and the coupled and uncoupled outbound staging areas withthe managed data area.
 4. The system of claim 3, further comprising: afront side data access layer and a back side data access layer, whereinthe external operational systems transfer control data through the frontside data access layer to the centralized master repository and transferreference data to and from the centralized master repository through theback side data access layer.
 5. The system of claim 4, furthercomprising: one or more of the enterprise-level business workflows isembedded within the system and is wholly or partially automated using anenterprise-level workflow engine tangibly embodied on acomputer-readable storage media to wholly or partially automate one ormore enterprise-level business processes and the mapping comprisestransformations that remain reasonably fixed over time; a logicalprocess layer tangibly embodied on a non-transitory computer-readablestorage media providing a context for implementing and wholly orpartially automating business configuration processes of the one or moreenterprise-level business workflows; a logical service layer tangiblyembodied on a non-transitory computer-readable storage media andunderlying the logical process layer, the logical service layerproviding service functions enabling process tasks for the automatedbusiness configuration processes; and a logical data layer tangiblyembodied on a non-transitory computer-readable storage media andunderlying the logical service layer, the logical data layer providingbase data models and physical representations for storing the manageddata of the enterprise for retrieval and use in connection with thebusiness configuration processes and service functions.
 6. A method ofcentrally managing managed data of an enterprise, comprising: providingan infrastructure services layer coupled with a centralized masterrepository and providing messaging between the centralized masterrepository and one or more external operational systems, the externaloperational systems permitted indirect access to managed data of theenterprise stored in the centralized master repository, theinfrastructure services layer further provides mapping between thecentralized master repository and the one or more external operationalsystems; providing a database comprising a cached data area comprisingcached data representing managed data of the enterprise extracted from amanaged data area in response to a processing request from one or moreinternal services and re-inserted into the managed data area followingprocessing from one or more internal services, one or more of theinternal services directly accessing the managed data of the enterprisestored in the centralized master repository; providing an inboundstaging area comprising one or more inbound staging tables and themanaged data area comprising one or more core master data management(MDM) tables, wherein inbound data is transferred from the one or moredata sources to the one or more inbound staging tables before the one ormore core MDM tables; providing outbound data to one or more datatargets; and when the outbound data is not sourced from the centralizedmaster repository, transferring the outbound data from the one or moreinbound staging tables to one or more outbound staging tables of anuncoupled outbound staging area before the one or more data targets;when the outbound data is sourced from the centralized masterrepository, transferring the outbound data from the one or more core MDMtables to one or more outbound staging tables of a coupled outboundstaging area before the one or more data targets; synchronizing datawithin the one or more core MDM tables with the outbound data in the oneor more outbound staging tables of the coupled outbound staging area andthe uncoupled outbound staging area; and wherein the managed data areastores the managed data of an enterprise as cached data in anintermediate state according to a manipulation process, the managed dataof the enterprise is maintained as locked in its true state for readonly access until completion of the manipulation process, outputting theintermediate state of the cached data related to the managed data of theenterprise to an entity of the enterprise.
 7. The method of claim 6,wherein during transfer of the inbound data from the one or more inboundstaging tables to the one or more core MDM tables, the internal servicesframework performs one or more of cleansing, validation, transformation,and processing of the inbound data.
 8. The method of claim 7, furthercomprising: synchronizing, by a syndication service, the inbound stagingarea and the coupled and uncoupled outbound staging areas with themanaged data area.
 9. The method of claim 8, further comprising:transferring, by the external operational systems, control data througha front side data access layer to the centralized master repository; andtransferring, by the external operational systems, reference data to andfrom the centralized master repository through the back side data accesslayer.
 10. The method of claim 9, further comprising: providing one ormore of the enterprise-level business workflows embedded within thesystem and wholly or partially automated using an enterprise-levelworkflow engine tangibly embodied on a computer-readable storage mediato wholly or partially automate one or more enterprise-level businessprocesses and the mapping comprises transformations that remainreasonably fixed over time; providing a logical process layer tangiblyembodied on a non-transitory computer-readable storage media providing acontext for implementing and wholly or partially automating businessconfiguration processes of the one or more enterprise-level businessworkflows; providing a logical service layer tangibly embodied on anon-transitory computer-readable storage media and underlying thelogical process layer, the logical service layer providing servicefunctions enabling process tasks for the automated businessconfiguration processes; and providing a logical data layer tangiblyembodied on a non-transitory computer-readable storage media andunderlying the logical service layer, the logical data layer providingbase data models and physical representations for storing the manageddata of the enterprise for retrieval and use in connection with thebusiness configuration processes and service functions.
 11. Anon-transitory computer readable media embodied with software thatcentrally manages managed data of an enterprise, the software whenexecuted using a computer system is configured to: provide aninfrastructure services layer coupled with a centralized masterrepository and provide messaging between the centralized masterrepository and one or more external operational systems, the externaloperational systems permitted indirect access to managed data of theenterprise stored in the centralized master repository, theinfrastructure services layer provides mapping between the centralizedmaster repository and the one or more external operational systems;provide a database comprising a cached data area comprising cached datarepresenting managed data of the enterprise extracted from a manageddata area in response to a processing request from one or more internalservices and re-inserted into the managed data area following processingfrom one or more internal services, one or more of the internal servicesdirectly accessing the managed data of the enterprise stored in thecentralized master repository; provide an inbound staging areacomprising one or more inbound staging tables and the managed data areacomprises one or more core master data management (MDM) tables, whereininbound data is transferred from the one or more data sources to the oneor more inbound staging tables before the one or more core MDM tables;provide outbound data to one or more data targets; and when the outbounddata is not sourced from the centralized master repository, transfer theoutbound data from the one or more inbound staging tables to one or moreoutbound staging tables of an uncoupled outbound staging area before theone or more data targets; when the outbound data is sourced from thecentralized master repository, transfer the outbound data from the oneor more core MDM tables to one or more outbound staging tables of acoupled outbound staging area before the one or more data targets;synchronizing data within the one or more core MDM tables with theoutbound data in the one or more outbound staging tables of the coupledoutbound staging area and the uncoupled outbound staging area; andwherein the managed data area stores the managed data of an enterpriseas cached data in an intermediate state according to a manipulationprocess, the managed data of the enterprise is maintained as locked inits true state for read only access until completion of the manipulationprocess, outputting the intermediate state of the cached data related tothe managed data of the enterprise to an entity of the enterprise. 12.The non-transitory computer readable media of claim 11, wherein: duringtransfer of the inbound data from the one or more inbound staging tablesto the one or more core MDM tables, the internal services frameworkperforms one or more of cleansing, validation, transformation, andprocessing of the inbound data.
 13. The non-transitory computer readablemedia of claim 11, wherein the software is further configured to:transfer control data through a front side data access layer to thecentralized master repository; and transfer reference data to and fromthe centralized master repository through the back side data accesslayer.
 14. The non-transitory computer readable media of claim 13,wherein the software is further configured to provide: one or more ofthe enterprise-level business workflows embedded within the system andwholly or partially automated using an enterprise-level workflow enginetangibly embodied on a computer-readable storage media to wholly orpartially automate one or more enterprise-level business processes andthe mapping comprises transformations that remain reasonably fixed overtime; a logical process layer tangibly embodied on a non-transitorycomputer-readable storage media providing a context for implementing andwholly or partially automating business configuration processes of theone or more enterprise-level business workflows; a logical service layertangibly embodied on a non-transitory computer-readable storage mediaand underlying the logical process layer, the logical service layerproviding service functions enabling process tasks for the automatedbusiness configuration processes; and a logical data layer tangiblyembodied on a non-transitory computer-readable storage media andunderlying the logical service layer, the logical data layer providingbase data models and physical representations for storing the manageddata of the enterprise for retrieval and use in connection with thebusiness configuration processes and service functions.